runtime: extract out allocate_stack_0
to work around a "Local Exec" TLS model issue and prevent segfaulting
#458
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
allocate_stack_0
writes the allocated stack toia2_stackptr_0
. Previously, this was done inline ininit_stacks_and_setup_tls
, which is defined in the main compartment withINIT_RUNTIME
, and thus may sometimes use the "Local Exec" TLS model and thus use a different thread-local address. Moving this toallocate_stack_0
inlibia2
forces it to use the correct GOT thread local.This is a workaround to #457, but doesn't actually fix the root issue, so I'm not sure if we should merge it instead of fixing #457 properly. But it does successfully prevent compartmentalized
dav1d
from segfaulting, and thus is included in #454.